Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Rest Api Compatibility] CommonTermsQuery and cutoff_frequency param #75896

Merged
merged 14 commits into from
Aug 5, 2021

Conversation

pgomulka
Copy link
Contributor

@pgomulka pgomulka commented Jul 30, 2021

Previously removed in #42654. The query and the parameter won't work under rest api compatibility and an exception with a message is returned advising that just use of match/multi_match is enough

relates #51816

pgomulka added 5 commits July 27, 2021 09:19
Refactoring to NamedXContentRegistry to make it easier to register new
query builders. It removes the concept of separate compatibel
namedXContentRegistry and adds a second dimension - restApiVersion - to
registry in NamedXContentRegistry.
This makes the design similar to the solution in ObjectParser where the
field parser lookup map also needs has a restApiVersion

relates elastic#51816
@pgomulka pgomulka changed the title Compat/common term query [Rest Api Compatibility] CommonTermsQuery and cutoff_frequency param Aug 2, 2021
@pgomulka pgomulka marked this pull request as ready for review August 3, 2021 12:23
@pgomulka pgomulka added the :Search/Search Search-related issues that do not fall into other categories label Aug 3, 2021
@elasticmachine elasticmachine added the Team:Search Meta label for search team label Aug 3, 2021
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-search (Team:Search)

@pgomulka pgomulka removed the WIP label Aug 3, 2021
@pgomulka pgomulka requested a review from romseygeek August 5, 2021 09:09
Copy link
Contributor

@romseygeek romseygeek left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One nit, LGTM otherwise


@Override
protected void doWriteTo(StreamOutput out) throws IOException {
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we throw UnsupportedOperationException here to make sure we catch inadvertent calls early?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Search/Search Search-related issues that do not fall into other categories Team:Search Meta label for search team v8.0.0-alpha2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants